Please include this file in any distribution of Passwords 1.0.
• Some comments & credits in Stack script were updated and fleshed out, giving the user some more ideas on how a few functions work.
• Please note the "cantModify" and "cantDelete" protect flags are set, but NOT password protected. They are only set to prevent HyperCard from increasing the FreeSpace. You can turn them off if you wish to modify the script. Please do not distribute any modified version.
Update list on v. 1.0d8 (final developmental version)
• All references to the function RANDOM have been removed and replaced by "any". This made the stack compatible with the Novy Quick30 accellerator, which has problems when HyperCard accesses the SANE function RANDOM.
• Compare external removed in favor of sumString used in previous version.
• Script contributed by Brian Molyneaux speeded up random character generation.
• The teletype sound has been commented out due to the annoyance of the author. This can be un-commented if you want to; the sound is still in the stack.
Update list on version 1.0d7
• Case sensitivity implemented by Mark Hanrek's Compare external.
Passwords 1.0d6 update list & bug fixes since version 1.0d4
• Special Characters button is longer to compensate for the substitute Chicago font I use.
• Removed extraneous white bits on main card paint layer
• About box contains more accurate info about Purdue U. and Prof. Eugene Spafford, from whom FL TODAY based the article I based my program from. Also added brief message to alert user of user agreement location.
• Now makes a teletype sound while generating passwords. Lemme know if you think this is too obnoxious.
• Passwords button is now named “New Passwords”
• A trap prevents “_” (underscore) character from being randomly generated, it is hard to see in some versions of Courier with the “show lines” option checked in a field. (unneeded when ANY was implemented in v. 1.0d8)
• Improved “message box version info handler” empties the message box after showing user version info. This is because “blind typing” was giving problems if the info was left in the message box.
• The version info handler now give a little cheer to the Ohio State Buckeyes.
• When clicking on the “about” button to go to the about background, there is a 20% chance Passwords will play “Across the Field,” the OSU fight song. Lemme know if you think this is too obnoxious.
• The About box bkgnd has 2 cards now, the second giving info about MacMAD, almost verbatim from the back of the March ’91 newsletter. I used the file-folder metaphor to switch between the 2 cards.
• More detailed user agreement and disclaimer in the top & bottom of the Stack script. Let me know if you think I should make any changes to this.
• An “on doMenu which” handler passes the “New Card” and “New Background” messages. (Now unneeded since I have set the cantModify to true.)
What I'm too lazy to fix: Just once I saw it generated a password that was to wide to fit in one line (“through the refrigerator”) - an extraneous “r” ended up on the next line, thus all following passwords in that field were pushed down one line. This left the last pw in that field not visible. I may have to widen the fields. Let me know what you think. I could write a small thing that counts the characters, or I could easily figure out which words in the list are the longest and make the fields wide enough to handle that many characters. That way the longest password possible would fit.
In the Future:
• I am thinking of adding a little code that uses more than just "the" in the prepositional phrases. "this", "that", "these", maybe even some code to handle plurals. But I think I'll wait to see what kind of response I get on this one.
• I might even fix that long-password problem.
• I am also considering adding "Hang on Sloopy" or another OSU song. How about it, Buckeye fans? GO BUCKS!
• I would like to replace the practice-password stuff with one that disguises the letters with •••• characters. I have seen some externals that so that, but they do not follow the exact guidelines I need. We'll see...
Many thanks to my beta-testers, previewers and scripting assistants.